Skip to main content

This is a new service – your feedback will help us to improve it.

Your data has issues

There is a problem

  • document-url column must have valid URIs
Reference Name Developer agreement type Planning application Document URL Notes Organisation Entry date Start date End date
S106-00222 section-106 PT15/2917/O

Invalid URI

2017-06-16 2017-06-16
S106-00223 section-106 PT15/2917/O

Invalid URI

2017-06-16 2017-06-16
S106-00358 section-106 PT15/0510/F

Invalid URI

2016-03-03 2016-03-03
S106-00360 section-106 PT15/0510/F

Invalid URI

2016-03-03 2016-03-03
S106-00669 section-106 PT15/0510/F

Invalid URI

2016-11-22 2016-11-22
S106-00660 section-106 PT15/0510/F

Invalid URI

2024-08-14 2024-08-14
S106-00125 section-106 P95/4605

Invalid URI

2008-05-14 2008-05-14
S106-00385 section-106 PT13/4182/O

Invalid URI

2017-11-08 2017-11-08
S106-00355 section-106 PK15/3950/F

Invalid URI

2016-11-10 2016-11-10
S106-00218 section-106 PT16/1176/RVC

Invalid URI

2016-12-05 2016-12-05
S106-00195 section-106 PT15/5535/RM

Invalid URI

2017-01-17 2017-01-17
S106-00196 section-106 PT15/5535/RM

Invalid URI

2017-01-17 2017-01-17
S106-00197 section-106 PT15/5535/RM

Invalid URI

2017-01-17 2017-01-17
S106-00192 section-106 PK02/2690/F

Invalid URI

2007-12-05 2007-12-05
S106-00187 section-106 PK04/2687/F

Invalid URI

2007-10-17 2007-10-17
S106-00188 section-106 PK04/2687/F

Invalid URI

2007-07-05 2007-07-05
S106-00181 section-106 PK06/2774/O

Invalid URI

2008-08-28 2008-08-28
S106-00182 section-106 PK06/2774/O

Invalid URI

2012-05-25 2012-05-25
S106-00259 section-106 PK06/2774/O

Invalid URI

2011-05-25 2011-05-25
S106-00379 section-106 PT07/2478/O

Invalid URI

2018-09-24 2018-09-24
S106-00380 section-106 PT07/2478/O

Invalid URI

2018-09-24 2018-09-24
S106-00381 section-106 PT07/2478/O

Invalid URI

2018-09-24 2018-09-24
S106-00382 section-106 PT07/2478/O

Invalid URI

2018-09-24 2018-09-24
S106-00383 section-106 PT07/2478/O

Invalid URI

2018-09-24 2018-09-24
S106-00237 section-106 PT07/2481/F

Invalid URI

2009-04-16 2009-04-16
S106-00238 section-106 PT07/2481/F

Invalid URI

2016-12-05 2016-12-05
S106-00662 section-106 PT08/2760/O

Invalid URI

2024-08-21 2024-08-21
S106-00210 section-106 PK16/5363/F

Invalid URI

2016-11-29 2016-11-29
S106-00209 section-106 PK16/0255/F

Invalid URI

2016-12-14 2016-12-14
S106-00228 section-106 PT06/0865/F

Invalid URI

2007-03-27 2007-03-27
S106-00397 section-106 PT06/0865/F

Invalid URI

2019-05-09 2019-05-09
S106-00398 section-106 PT06/0865/F

Invalid URI

2019-05-09 2019-05-09
S106-00399 section-106 PT06/0865/F

Invalid URI

2019-05-09 2019-05-09
S106-00278 section-106 PK16/2577/O

Invalid URI

2017-07-17 2017-07-17
S106-00242 section-106 PK17/0807/F

Invalid URI

2017-11-07 2017-11-07
S106-00271 section-106 PT17/1761/O

Invalid URI

2017-11-13 2017-11-13
S106-00250 section-106 PT09/0948/F

Invalid URI

2009-12-16 2009-12-16
S106-00257 section-106 PT17/4800/O

Invalid URI

2017-12-18 2017-12-18
S106-00409 section-106 PT17/4800/O

Invalid URI

2019-08-29 2019-08-29
S106-00295 section-106 PK17/2020/F

Invalid URI

2018-08-08 2018-08-08
S106-00269 section-106 PT17/2444/O

Invalid URI

2018-01-29 2018-01-29
S106-00263 section-106 PT17/3446/F

Invalid URI

2018-02-20 2018-02-20
S106-00264 section-106 PT17/3446/F

Invalid URI

2018-02-20 2018-02-20
S106-00265 section-106 PT17/3446/F

Invalid URI

2018-02-20 2018-02-20
S106-00266 section-106 PT17/3446/F

Invalid URI

2018-02-20 2018-02-20
S106-00577 section-106 PT17/3227/F

Invalid URI

2018-02-20 2018-02-20
S106-00579 section-106 PT17/3227/F

Invalid URI

2018-02-20 2018-02-20
S106-00537 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00539 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00541 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27

Showing rows 51 to 100 of 489

How to fix this issue

Your dataset is missing the document-url column.

The Developer agreement guidance explains how to fix the issue:

document-url

How to improve South Gloucestershire Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL